Transaction Codes

This tab contains the transaction codes added for the current query.

This tab provides you with an overview of all Transaction Codes which are related to this particular Query.

A: If you uncheck a T-code here, it will not be taken into account when running an audit.

B: Indication of the T-code.

C: If you uncheck a T-code here, it will not be possible to retrieve STAD-data for this particular T-code (meaning that you will not be able to calculate which users actually ran this Transaction).

D: Description of the T-code (Not available when there is no Master-Data database attached to the application).

E: Click this button to run the query (= audit on Transaction Code level).:

The CSI AA enables you to investigate which users have a certain access to a particular set of transaction codes.

In order to do so, make sure to select all transaction codes you wish to check. Deselect those you do not need to be investigated.

Clicking the 'Run S_Tcode'-button will generate a result screen which provides you with an overview of all users and information regarding the authorizations they have for the selected transaction codes.

Additional information such as norm and STAD-status are also available at this result screen.

Double-clicking on the numbered heading (which represent the transaction codes) triggers a dialog box with a legenda of the transaction codes you have included in this run.

Logically, the button T_Code at the bottom of the screen is not included, since every user in the Result Screen has at least one transaction code he or she can execute in the SAP system. However, you can modify Logic and Norm settings by clicking AND/OR or Yes/No.

F: Clicking this button will activate the Simulation screen.

G: By checking this tick-mark you will make sure that in the Result Preview and/or in the Result container it will not be possible to choose whether you display the T-code access for each user.

Tip: This option must be used in situations where you run a query where no T-codes are assigned to the query (eg DEBUA) since otherwise one might underestimate security risks related to those queries.